Keysight SystemVue 2023

PathWave System Design (SystemVue) 2023 Release Notes

• (W4800B) PathWave System Design Core
• (W4501E) PathWave Comms/DSP Simulation
• (W4502E) PathWave RF Simulation
• (W4503E) PathWave Phased Array Simulation
• (W4519E) PathWave DPD Designer
• (W4522E) PathWave 5G and Cellular Library
• (W4523E) PathWave Wifi and Connectivity Library
• (W4526E) PathWave Aerospace Defense Library
• Known Issues
• Licensing and Installation
• Documentation

(W4800B) PathWave System Design Core

Enhancements

• Python Scripting Enhancements

  • Updated Python version support: PathWave System Design 2023 requires Python 3.10.x.

    This version introduces breaking changes and may lead your existing scripts to fail or work incorrectly.

  • Python scripting has been extended to add support for graphs and also adds a new graph image capture function for high-resolution images:  export_graph_as_image(filename, format, width, height, resolution). For more information, see the  Python Scripting  documentation.

  • The Python API now supports:

    • creating workspace variables.

    • ability to change the design name of an analysis. Changing the design name of the analysis will also change the design of the analysis. The design name is a property of analysis.

    • opening and closing graph windows, as well as a function to get a list of available graphs. For more information, see Python Graph Class.

    • setting the dataset for analysis.

    • setting the dataset reference for a graph.

  • The Python Workspace object now has a "designs" property that returns a dictionary of all designs in the workspace.

  • The Visual Source Code extension for PathWave System Design Python scripting with editing and debugging capabilities has been published to the  Visual Studio marketplace. For more information, see  VS Code System Design Python Extension.

• Graph Enhancements

  • Graph objects now have an option called Auto-Unit which is on by default. This feature selects an appropriate unit from the variable's available units so that the numbers of the axis range look nice on the graph.

  • Markers on Graph objects now support dragging. Click any marker label and drag the marker to the desired location on the trace. Markers can not be dragged across traces.

  • The auto-scale algorithm for axis ranges on graph objects has been improved. The x-axis and y-axis ranges should calculate a range with a step size divisible by 1, 2, 5, or 10. The axis range may be adjusted above and/or below the data minimum to calculate a nice step size. In addition, graph objects now have an option called Auto-Unit which is on by default. This feature selects an appropriate unit from the variable's available units so that the numbers of the axis range look nice on the graph

  • The graph axis provides a new Auto-Unit setting, which is used in conjunction with Auto-Scale to determine the most appropriate unit for the data range.

    Auto-Unit is ignored when a Label is specified because the unit is only appended to the automatic label. Since the unit will be omitted (unless it's part of the user-entered Label text), there is no way to visually determine the automatic unit.

  • The graph markers have been enhanced to display the market text in a separate window. This allows the market window to be resized in case of long text and also allows the info to be scrolled.

• General Enhancements

  • Shift+F5, now Runs all the analyses associated with the active Design. Previously this command was associated with the "Revert to Original Settings" action. That command is now Alt+Shift+F5.

  • When editing a schematic, a user may now select all instances of a given model type. This option is available when the user has exactly one type of model selected. To do this the user should right-click on an instance of the desired part (with the corresponding model) and choose "Select all instances of model" (also available in the main menu  Schematic > Select All Instances of Model). The user can then operate on this selection group to perform various actions, including "Disable to short", "Disable to open", or deletion.

  • The schematic part text has been improved for non-scalar parameters. 

    • Parameters with errors are still drawn in red, but vector and array values will no longer be incorrectly flagged as errors when the model uses non-array validation types.  This means that scalar parameters will not show an error on the schematic when assigned a vector or array value. 
    • Only the first 100 elements of a vector or array are checked for validity, so it's possible that an erroneous non-scalar parameter is not highlighted on the schematic.  These types of errors will only be reported when an analysis is actually run.  
    • Out-of-range values (and other warnings) are now drawn in orange, not purple.

  • SystemC is no longer supported.